-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add coverage command for ci unit tests #332
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Datadog ReportBranch report: ✅ 0 Failed, 13 Passed, 0 Skipped, 13.47s Total Time |
de9ef4c
to
5c077a4
Compare
package.json
Outdated
@@ -24,6 +24,7 @@ | |||
"test:vitest": "dotenv -e .env.test vitest run", | |||
"test-dev:vitest": "dotenv -e .env.test vitest", | |||
"test:e2e": "dotenv -e .env.test playwright test", | |||
"test-ci:coverage": "vitest run --coverage", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: Why not dotenv -e .env.test
instead?
1d361e1
to
b1c90e9
Compare
feat: add coverage command for ci unit tests
feat: update autogenerated msw script